home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19951130-19960209
/
000123_news@columbia.edu_Sat Dec 16 22:41:28 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA08667
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun>); Sat, 16 Dec 1995 17:42:32 -0500
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.6.12/8.6.12) id RAA00488 for kermit.misc@watsun; Sat, 16 Dec 1995 17:41:31 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Uploading into EDT editor
Date: 16 Dec 1995 22:41:28 GMT
Organization: Columbia University
Lines: 61
Message-Id: <4avhuo$f6@apakabar.cc.columbia.edu>
References: <4aronp$ks5@huron.eel.ufl.edu> <1995Dec15.165002.69763@cc.usu.edu> <4aua85$f52@huron.eel.ufl.edu>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <4aua85$f52@huron.eel.ufl.edu>,
David A. Johns <afn10375@freenet4.freenet.ufl.edu> wrote:
: In <1995Dec15.165002.69763@cc.usu.edu>, jrd@cc.usu.edu (Joe Doupnik) wrote:
:
: # You are placing new text into a full screen editor. EDT
: # wants to move the cursor around as a result, rather than
: # simply echoing CR back to MSK. Consequently, what EDT does
: # echo comes out as one line overlapping the next on your MSK
: # screen, but the text is actually inserted properly. This is
: # typical of full screen editors when inserting material in the
: # middle (and sometimes even at the end) of a document. Just
: # ignore the false echoing and do that screen refresh after
: # reentering Connect mode.
:
: OK, but what about having to keep hitting <enter> to keep the upload
: going? Does that ring any bells?
:
Unless you use the SET TRANSMIT command to change things, the TRANSMIT
command works by reading a line of text from the source file, stripping
the line terminator(s) from it, then sending the line of text, then
sending a carriage return, and then waiting for a linefeed to echo back.
This simulates exactly what would happen if you were typing the lines
of text yourself.
Kermit waits a pretty long long time (not sure exactly how long in the
case of MS-DOS Kermit) for the linefeed to echo, so if the host does not
always echo a linefeed, as evidently EDT does not, there will be a lot of
inactivity. MS-DOS Kermit lets you wake up a stuck TRANSMIT by hitting
the enter key.
Let's see what's really happening. Log into VMS, start EDT, then escape
back to MS-DOS Kermit and put it into debugging mode with SET DEBUG
SESSION. Then start typing lines into EDT's buffer. What do we see?
The first 20 lines or so are echoed as:
<text><CR><LF><ESC>[L
(<ESC>[L is "insert line", which moves the "[EOB]" indicator down.) Old
lines stand still, new lines "go down". Kermit sees the linefeed and
immediately sends the next line.
But then, when the bottom of the screen is reached, EDT's screen updating
method changes. From now it sends explicit screen-formatting codes and
no more linefeeds. Old lines "go up", and the new line is always at the
bottom, just above the "[EOB]". This explains the symptoms you have seen.
Thus there is no single character that can be used by Kermit to serve as
an indicator that the line just transmitted has been received. Linefeed
only works for the first screen. You could try ESC, but after the first
screen there are several ESC characters per line. So first just try:
set transmit prompt \0
which means, don't wait for any character -- just keep sending the lines
(make sure you've got good flow control). I tried it here on a file that
has several hundred lines and EDT accepted it without loss or complaint.
But in case this overruns EDT, then you can also "set transmit pause n"
to have Kermit pause n milliseconds after sending each line.
- Frank